About Precedence
Precedence works to override content from the top (parent) to the lower (child) organizations. For example, all base content fragments that might be included in a document are attached to the Wolters Kluwer Financial Services precedence level and may be overridden at any other level in the hierarchy. If Organization 2 overrides a particular content fragment, documents assembled in the context of Organization 5 or Organization 6 will incorporate the override rather than the base version of that fragment, but organizations 4, 9, and 10 would be unaffected. Each organization in the precedence hierarchy is identified by a Universal Unique Identifiers (UUID).
Several organizations may exist in an enterprise and relate to each other in a hierarchical fashion; precedence is the expression of that organization hierarchy. Wolters Kluwer Financial Services is always at the top of the hierarchy and the financial institution and suborganizations (e.g., lines of business) are below.
- Utilize base Expere Knowledge Base content (language, rules, etc.)
- Supersede base Expere Knowledge Base or other parent\ancestor organization content at a particular org level and its descendents
- Create custom content for use at a specific org level and its descendents
When the document assembler encounters two or more components with the same name that meet the requirements of the needed document, the assembler chooses the component based on precedence, which is a process by which the system selects document components according to the identity of the entity requesting the document, or, if no matching component is found, according to the identity of one of the entity’s parents or ancestors. If no match is found, a default component is provided. This concept is referred to as “precedence” or “owner precedence.”